@Alberto-Brosich These have not been ported 22 or 23, but you can find the source in the 18.6 branch. Depending on your requirements, you may need to modify the code. I need to migrate oniondebug myself so will do that in the next day or so, since I need it for powerdock. Some of these libraries may be dependent on the OpenWrt 18 GPIO numbering which changed in OpenWrt22. I think @luz made patch for this, check his profile for posts. Personally I'm just adopting the new numbering system.

@crispyoz Thank

@crispyoz Thank you, I will do this now

@jcrfMX There is a lot of info on LVGL Forum that can adress your concerns. @Lazar-Demin is correct in that the errors being reported indicate you have not correctly added the lvgl headers and libs to your include path library paths. There is nothing special about using LVGL in a C++ application compared to any other C/C++ project, the LVGL Forum has numerous discussions related to this but there's nothig unique about LVGL in this. With regard to the Dash and LVGL, the main area you need understand is the lv_conf.h and the driver configuration, other than that the Dash is a like any other LVGL project.

@luz Thank you your reply, this is very helpful for me to understand Onion and OpenWrt related knowledge. Thanks~~~

@MarshalllGG Yes you can compile on say Linux but you have to run the app on your Omega2. Sometimes if I am developing an app I might do the skeleton of the work on my Linux system and test it on Linux without all the Omega2 specific stuff. Once I have that all correct I then start adding the Omega2 specific stuff and then need to test it on the Omega2.

@crispyoz I correct the issue with this commands : ./scripts/feeds update onion ./scripts/feeds update -a from this repository https://github.com/OnionIoT/source

Due to the lack of comments it is not clear, the topic is not interesting, either too simple or too complicated. I will describe what happened to me, maybe someone will come in handy. Instruction to create pjsip ipk + alsa. 1 Install OpenWRT Build System (in my case on Linux Mint 19.3) follow the manual. https://docs.onion.io/omega2-docs/cross-compiling.html Then. ol@ol-VirtualBox:~/OpenWRT-builds/onion_tst$ cd source/ $ ./scripts/feeds update -a $ ./scripts/feeds install -a $ make menuconfig Target System (MediaTek Ralink MIPS) Subtarget (MT76x8 based board) Target Profile (Multiple devices) [*] Target Devices/ (Onion Omega2+) Select telephony & alsa * Libraries/alsa-lib * Sound/alsa-utils * Libraries/Telephony/libpj * Libraries/Telephony/libpjlib-util * Libraries/Telephony/libpjmedia * Libraries/Telephony/libpjnath * Libraries/Telephony/libpjsip * Libraries/Telephony/libpjsip-simple * Libraries/Telephony/libpjsip-ua * Libraries/Telephony/libpjsua <*> Libraries/Telephony/libpjsua2 2 edit Makefile: <build-system>/source/feeds/telephony/libs/pjproject/Makefile // ln:38 add "+alsa-lib" DEPENDS:=$(CXX_DEPENDS) +libopenssl +libuuid +libpthread +alsa-lib // ln:65 change --disable-g711-codec // to --enable-g711-codec // ln:81 change --disable-sound // to --enable-sound If the first build (no toolchain) need run. $ make This make will create toolchain, image and ipk pakages. If there is a toolchain and you only need to create a pjsip packages, run. $ make package/feeds/telephony/pjproject/compile Result in. <build-system>/source/bin/packages/mipsel_24kc/telephony libpj_2.7.2-2_mipsel_24kc.ipk libpjlib-util_2.7.2-2_mipsel_24kc.ipk libpjsip_2.7.2-2_mipsel_24kc.ipk libpjnath_2.7.2-2_mipsel_24kc.ipk libpjmedia_2.7.2-2_mipsel_24kc.ipk libpjsip-simple_2.7.2-2_mipsel_24kc.ipk libpjsip-ua_2.7.2-2_mipsel_24kc.ipk libpjsua_2.7.2-2_mipsel_24kc.ipk libpjsua2_2.7.2-2_mipsel_24kc.ipk libsrtp2_2.1.0-1_mipsel_24kc.ipk My Omega2+: Ω-ware: 0.3.2 b239 Copy ipk files to Omega2 & install, in that order. root@Omega-A0E7:~/projects/ipk_my# opkg install libpj_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjlib-util_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjsip_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjnath_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjmedia_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjsip-simple_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjsip-ua_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjsua_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libpjsua2_2.7.2-2_mipsel_24kc.ipk root@Omega-A0E7:~/projects/ipk_my# opkg install libsrtp2_2.1.0-1_mipsel_24kc.ipk Install alsa from repository or from ipk files. root@Omega-A0E7:~/# opkg update root@Omega-A0E7:~/# opkg install alsa-utils Testing. Link to application, config & ipk https://drive.google.com/drive/folders/1Zr51okC9FJEvxXGqvt_Dmsm4doboAgEL?usp=sharing <streamutil-win> folder include streamutil application for windows, copy this folder on windows computer, edit ip address of Omega2 cli-streamutil-Tx-Unicast.bat & run cli-streamutil-Tx-Unicast.bat I am used Ethernet extention. Config Ethernet port of Omega2. Set same subnet for win & omega. <streamutil-omega> folder include streamutil application for OpenWRT, on Omega2 copy files streamutil and sutil_rx_ucast.sh & run sutil_rx_ucast.sh. The folder also contains files for building the project. <ipk> folder include ipk files for pjsip building with alsa support. .config: my menuconfig file.

@tjoseph1 I wrote it because I messed up my Netbeans installation and had to work it out all over again. I decided to put it on here so I wouldn't lose the instructions

@asyxcv, you should compile it manualy, next link will be usefull: How to compile C/C++ native applications You are trying to use old manuals about LEDE. Another way your project has also special manifest for the OpenWRT system (see snapcast/openWrt/Makefile.openwrt) it needs to make .ipk-files (packages) for the opkg util. But this file is old and needs to be fixed. And last: making your own packages for opkg is very difficult task for masters. More infirmations about it you can get from OpenWRT official documents, community and examples.

@crispyoz I set up this machine to dual boot with a fresh copy of Ubuntu 18.0.4 installed. It took some time and a few false turns, but I'm able to compile my own 'hello world' file now: file hello hello: ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked, interpreter /lib/ld-, with debug_info, not stripped Next I'll work on rsync, etc, to automatically move the final build to my Omega 2+. Thanks for the suggestion of running outside a virtual machine.

@volkan-ünal, If you post same error, you are newbie in cross-compilation. It's thorny way but you choose right direction for it. You can take my template to start create your own applications, then translate and publish my README.md file from Russian into English for a someone else, because my English is poor. Follow to the link about.

Hi all! I glad to show my template of project Hello world that uses CMake build system, it's named as myapptemplate. My last sample was use GNU Autotools, it's a difficult system. Today we have many projects with CMake (cmake.org). For new projects I recommend use CMake. But it will have problems with cross-compilation for beginners. Let's find it out! Step 1. Creating you own CMake project First you have to install git and cmake applications in the host if there are none. Next follow into you projects directory in the host, e.g. $HOME/projects and clone there my CMake template myapptemplate project. Then enter new project directory and remove .git dir from there. git clone --single-branch --branch CMake https://bitbucket.org/hlorka/myapptemplate.git <my_app_name> cd ./<my_app_name> rm -rf ./.git The files CMakeSettings.json and myapptemplate.vcxproj for MS Visual Studio IDE and can be deleted too. Step 2A. General compilation for the host machine It's very simple. First you have to configure and make cache CMake's files. Look at the command below: cmake . [--config Debug] --config Debug will append debug information (symbols) and postfix -d to the output binary file (helloworld-d). Then you can build (compile) project, using next commands below Via CMake: cmake --build . [--clean-first] Or via Makefile (make utility) make Step 2B. Cross-compilation using OpenWRT SDK First open file cross-compile/openwrt-mips-toolchain.cmake for modify. nano ./cross-compile/openwrt-mips-toolchain.cmake Fragment of this file below: ... # Локальные переменные set(openwrt_sdk_dir $ENV{HOME}/OpenWRT-sdk) # Экспортируемая переменная, в скрипт `xcmake.sh` set(staging_dir ${openwrt_sdk_dir}/staging_dir) set(toolchain_dir ${staging_dir}/toolchain-mipsel_24kc_gcc-7.3.0_musl) ... You have to check/modify OpenWRT SDK paths. Next run cmake with parameters: cmake -DCMAKE_TOOLCHAIN_FILE=./cross-compile/openwrt-mips-toolchain.cmake [--config Debug] [-DREMOTE_INSTALL_IP=<remote-IP> -DREMOTE_INSTALL_USER=root] Parameters REMOTE_INSTALL_* will make targets to help you copy binary files to the Omega via rsync. You also need SSH access by key. To build (cross-compile) project you have to run script: ./xcmake.sh --build . [--clean-first] Step 3 (optional). Remote-installation If you set REMOTE_INSTALL_* parameters, after build you able using remote-install, remote-uninstall targets for example below: cmake --build . --target remote-install or make remote-install Step 4 (optional). Making IPK-package After cross-compilation you will see files openwrt-manifest-git.mk, openwrt-manifest-local.mk in the root project directory. There are two variants of manifest (renamed Makefile). openwrt-manifest-git.mk - variant of manifest file of project to make package that sources will be download from Git repository. openwrt-manifest-local.mk - variant of manifest file of project to make package localy. It's useful for debugging or internal using. To make package, first you have to create feed directory outside this project, e.g. $HOME/my-openwrt-packages. Create sub-directory in it with you project name, e.g. $HOME/my-openwrt-packages/<my_app_name> Then make symlink there for one of the Manifest file, e.g.: ln -sf $HOME/projects/<my_app_name>/openwrt-manifest-local.mk $HOME/my-openwrt-packages/<my_app_name>/Makefile Next change working dir to the root of OpenWRT SDK. Open file feeds.conf.default in any text editor and append your own feed there like below string. ... src-link my_packages /home/<my_user_name>/projects/my-openwrt-packages Then run once sequence of commands: ./scripts/feeds update my_packages ./scripts/feeds install <my_app_name> Now you can build IPK-package: Variant openwrt-manifest-local.mk: make package/<my_app_name>/prepare make package/<my_app_name>/compile Variant openwrt-manifest-git.mk: make package/<my_app_name>/download make package/<my_app_name>/compile Your IPK-files you can find in the directory <OpenWRT_SDK_dir>/bin/packages/mipsel_24kc/my_packages. It will named like <my_app_name>_1.0-1_mipsel_24kc.ipk To install package from IPK-file in the Omega, run next command: opkg install ./<my_app_name>_1.0-1_mipsel_24kc.ipk

@El-Berto this is an older mutex type, you may need to migrate the code.

@OSO-Bear my guess would be that you are using dynamic linking and have a version mismatch in your libraries. Try statically linking and if this is successfully take a look at the versions you are compiling and and running against.

@Andres-Santos Most compilatoin issues can be resolved using the following steps: ./scripts/feeds clean ./scripts/feeds update -a ./scripts/feeds install -a make -j6 If that fails I will usually make clean before make -j6

@crispyoz Thanks! It resolve the problem. Regards!